Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.

After Xcode 26.1 was updated and installing the OS 26.1 simulators, my app started crashing related to transformable properties. When I checked my schema, I noticed that properties with array collection types are suddenly set with an option transformable with Optional("NSSecureUnarchiveFromData")], even though I do not use any transformable types. I verified the macros, no transformable was specified. This is causing ModelCoders to encode/decode my properties incorrectly. This is not an issue when I switch back to OS 26.0 simulators.

Hello, While setting up Xcode Cloud using Bitbucket, I encountered an issue with Source Control and providing access to the repository. The problem most likely stems from the fact that Bitbucket has updated its policy, and the use of app passwords is no longer available (at least for new ones). However, in Xcode → Settings → Source Control, the login flow still requires an app password, which makes it impossible to authenticate using the new API tokens. Attempting to authenticate via SSH also does not resolve the issue. After connecting to GitHub, I also tried to connect through the web version, but I'm getting the same message: "Bitbucket Cloud installation was incomplete." I received this same message when I first tried to connect through Xcode. This problem does not occur when connecting to GitHub. I would appreciate receiving feedback from the Apple team on this issue. System Info: Xcode: 16.2 (latest from App Store) macOS: Sequoia 15.1

I've recently installed 26.1 Beta 3 alongside stable 26.0.1 When building my app with 26.0.1 the final .ipa size is ~17mb, however after building my app with 26.1 Beta 3 the size has increased up to ~22mb The main difference is Assets.car blowing from 1.1mb to 5.6mb (or 8.6mb if I include all icons settings). Upon examining I've found new liquid glass .icon file duplicating itself multiple times as png variants (any, dark, tinted, etc). Is anyone else experiencing this issue?

I have made a screensaver for mac in swift, but couldn't find how to add an icon the logo image that shows up on saver file) and thumbnail (the cover image that shows up in the screensaver catalogue). Currently, it just shows a default blue spiral galaxy thumbnail and no icon image

Hey! I am writing type formatting scripts in Python for lldb, as described in https://lldb.llvm.org/use/variable.html#python-scripting. I'm trying to pass an environment variable to lldb from Xcode to determine the path to the scripts in the project root, so the project is not bound to some predetermined path. I am having trouble doing this in Xcode. What I have tried: lldbinit file Create a .lldbinit file in $(SRCROOT) with the following content: platform shell echo $SRCROOT. Set the path to the .lldbinit file in Edit Scheme... > Info > LLDB Init File ($(SRCROOT)/.lldbinit). Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments > Environment Variables. entry-point breakpoint Add a breakpoint to the entry-point of the application. Set the Automatically continue after evaluating actions option. Add the action platform shell $(SRCROOT) or platform shell $SRCROOT. Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments > Environment Variables. What I expect to happen: The first line of the debug console is a path pointing to $(SRCROOT) What actually happens: No path is output Is this functionality available in Xcode Version 26.0.1 (17A400)? Thanks in advance, Barnabas

I have a Catalyst app ('container') which hosts an embedded AUv3 Audio Unit extension ('plugin'). This used to work for years and has worked with this project until a few days ago. it still works on iOS as expected on MacOS the extension is never registered/installed and won't load extension won't show up with AUVal seems to have stopped working with the 26.1 XCode update I'm fairly certain the problem is not code related (i.e. likely build settings, project settings, entitlements, signing, etc.) I have compared all settings with another still-working project and can't find any meaningful difference (I can't request code-level support because even the minimal thing vastly exceeds the 250 lines of code limit.) How can I debug the issue? I literally don't know where to start to fix this problem, short of rebuilding the entire thing and hope that it magically starts working again.

Hello All, I’m a mobile-app developer working with iOS 26+ and I’m using BGContinuedProcessingTask to perform background work. My app’s workflow includes the following business logic: Loading images via PHImageRequest. Using a CLIP model to extract image embeddings. Using an .mlmodel-based model to further process those embeddings. For both model inferences I set computeUnits = .cpuAndNeuralEngine. When the app is moved to the background, I observe that the same workload(all three workload) becomes on average 4-5× slower than when the app is in the foreground. In an attempt to diagnose the slowdown, I tried to profile with Xcode Instruments, but since a debugger was attached, the performance in background appeared nearly identical to foreground. Even when I detached the debugger, the measured system resource metrics (process CPU usage, system CPU usage, memory, QoS class, thermal state) showed no meaningful difference. Below are some of the metrics I captured: Process CPU: 177% (Foreground) → 153% (Background) → ~-24.1% Still >1.5 cores of work. System CPU: 56.1% → 38.4% → ~-17.7% Process Memory: 244.8 MB → 218.1 MB QoS Class: userInitiated in both cases Thermal State: nominal in both cases Given these results, I’m finding it hard to pinpoint why the overall latency is so much worse when the app is backgrounded, even though the obvious metrics show little variation. I suspect the cause may involve P-core vs E-core scheduling, or internal hardware throttling/limit of Neural Engine usage, but I cannot find clear documentation or logging to confirm this. My question is: Does anyone know why a CPU (and Neural Engine)-intensive job like this would slow down so dramatically when using BGContinuedProcessingTask in the background on iOS 26+, despite apparent similar resource-usage metrics? Are there internal iOS scheduling/hardware-allocation behaviors (e.g., falling back to lower-performing cores when backgrounded) that might explain this? Any pointers to Apple technical notes, system logs, or instrumentation I might use to detect which cores or compute units are being used would be greatly appreciated. Thank you for your time and any guidance you can provide. Best regards,

When xcode is installed on a mobile phone, the first run always fails. The second run usually works normally.The certificate signatures have been checked and all are normal。This problem will also occur if you stop the running xcode and then run it again。please help me. Mac mini:Apple M2 Pro mas os 15.2 (24C101) Xcode: Version 16.2 (16C5032a) The first failed print is as follows: 无法安装“xxx” Domain: IXUserPresentableErrorDomain Code: 14 Recovery Suggestion: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.uRA3Gt/extracted/Payload/xxx.app : 0xe8008001 (An unknown error has occurred.) User Info: { DVTErrorCreationDateKey = "2025-11-20 02:50:17 +0000"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } Failed to install the app on the device. Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { NSURL = "file:///Users/shenchunxing/Library/Developer/Xcode/DerivedData/VideoGo-dwhfrhswidapcydbmfuamplrtvso/Build/Products/Debug-iphoneos/xxx.app"; } 无法安装“xxx” Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: 无法安装此App，因为无法验证其完整性。 Recovery Suggestion: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.uRA3Gt/extracted/Payload/xxx.app : 0xe8008001 (An unknown error has occurred.) Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.uRA3Gt/extracted/Payload/xxx.app : 0xe8008001 (An unknown error has occurred.) Domain: MIInstallerErrorDomain Code: 13 User Info: { FunctionName = "+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]"; LegacyErrorString = ApplicationVerificationFailed; LibMISErrorNumber = "-402620415"; SourceFileLine = 79; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_identifier" = "00008120-0009758221C2201E"; "device_isCoreDevice" = 1; "device_model" = "iPhone15,4"; "device_osBuild" = "18.2 (22C152)"; "device_platform" = "com.apple.platform.iphoneos"; "device_thinningType" = "iPhone15,4"; "dvt_coredevice_version" = "397.28"; "dvt_coresimulator_version" = "993.7"; "dvt_mobiledevice_version" = "1759.60.7"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 13228; "operation_errorCode" = 14; "operation_errorDomain" = IXUserPresentableErrorDomain; "operation_errorWorker" = IDEInstallCoreDeviceWorker; "operation_name" = IDERunOperationWorkerGroup; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_113575882_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_mtc_enable" = 1; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos18.2"; "sdk_osVersion" = "18.2"; "sdk_variant" = iphoneos; }

My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work... I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...

In the official explanation, "deployment targets" refers to "the OS range supported by this version of Xcode for uploading apps to App Store Connect." On the Xcode Support page (https://developer.apple.com/support/xcode/), I can find the deployment targets supported by each Xcode version. My question is: can I use a newer version of Xcode to build an IPA with an older deployment target that isn’t listed? For example, can I use Xcode 26 to build an iOS 12 IPA (just build, not debug)? In my opinion, since the new SDKs still contain many old macros restricted to earlier iOS versions, it should be possible, but I’m not sure if that’s correct. Thanks.

Since a few days, I'm trying to fetch our private SPM repo hosted on Azure via Xcode but without success. Actually they now accept only ssh key RSA-SHA2-256 or RSA-SHA2-512. So I created a new SSH key, but it seems the problem persists when I try to fetch spm repo or git clone via xcode: "You’re using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7) (-20)" Even so I'm choosing the good new ssh key, it seems Xcode is sending wrong information about the new generated ssh key. Anyone is experiencing the same here?

Is Xcode 26 required for DeclaredAgeRange APIs? We ask because there appears to be a serious legal deadline on January 1, 2026 and if Xcode 26 is required to meet this deadline, it's about to be a huge burden for us to upgrade to it over the holidays. Our app does support teenagers.

An error occurred preventing Xcode from downloading version information from App Store Connect for account "xxxxxxxx". An unexpected error occurred: [<__NSDictionaryM 0x600003ed4fe0> valueForUndefinedKey:]: this class is not key value coding-compliant for the <app name! 5.00.12 (iOS App). I have no idea what the hell is causing this. I have checked all of the links between screens and objects and none are missing. This is a live active version on the store.

I'm using Xcode Cloud to build for internal TestFlight testing. But it stuck in Archive. No warning or error. Unable to complete the workflow. What could be causing this? I have absolutely no idea what to do now.

I'm unable to sign the an example application using xcode and "automatically manage signing". The error I'm getting is: CodeSign [...] (in target 'foobar' from project 'foobar') Signing Identity: "Apple Development: [xxxx] " /usr/bin/codesign --force --sign 4ABB258102FF656E9F597546A49274C28D2B8B3E -o runtime --timestamp\=none --generate-entitlement-der [filename] 4ABB258102FF656E9F597546A49274C28D2B8B3E: no identity found Command CodeSign failed with a nonzero exit code However, I am able to see a certificate and a private identity on my keychain: % security find-certificate -aZ | grep -i 4ABB258102FF656E9F597546A49274C28D2B8B3E SHA-1 hash: 4ABB258102FF656E9F597546A49274C28D2B8B3E and % security find-key -s | grep -q 'Apple Development' && echo YES YES what is puzzling is that security does not find an identity: % security find-identity -p codesigning Policy: Code Signing Matching identities 0 identities found Valid identities only 0 valid identities found but XCode claims that everything is working fine. Anybody knows what might I be missing? I tried logging out, requesting new certificates, rebooting, moving them to another keychain, and asking to developer friends.

I have an Xcode app where currently txt files in the project display text data as a list. I can search through the lists and have buttons that will swap between different lists of information that you can look through. The next task is I have URL connections to docx files on a SharePoint site. I am trying to use an URLsession function to connect to the URL links to download the documents to the document directory then have the application read the doc information to then be displayed as the txt info would. The idea is that the docx files are a type of online update version of the data. So when the app is used and on wifi, the app can update the list data with the docx files. I have code set up that should access the URL files but I am struggling to figure out how to read the data and access from this Documents directory. I have been looking online and so far I am at a loss on where to go here. If anyone can help or provide some insight I would greatly appreciate it. I can try and provide code samples to help explain things if that is needed.

I’m developing a Safari App Extension and I want to debug the background.js script. However, I can’t find any tool or option to do this. When I run the extension from Xcode using the ProjectName Extension (macOS) scheme, I expect to see a “ProjectName” item under the Develop → Web Extension Background Content menu. But there’s nothing there. Has anyone encountered the same issue? How did you fix it? Environment: Manifest Version: V3 Safari: 26.0.1 (21622.1.22.11.15) Xcode: 26.0.1 (17A400)

Several app developers are struggling with the inability to provide a separate app icons that looks nice on older macOS versions while at the same time provide Icon Composer icons that look great on macOS Tahoe 26. An ability to provide separate icons is super important to those who have app icons that follow the curvature of the default icon borders (as the corner rounding radius is different for Sequia and Tahoe). Take a look at this for example: https://github.com/ghostty-org/ghostty/issues/7564#issuecomment-3042061547 Question: Is there a definitive/recommended way to address this issue? How can a developer add a glass icon variant that looks good on Tahoe and provide a bitmap icon for older macOS versions? Some background info: Prior to Xcode 26 beta 4, one could add an App Icon to Assets to be used as app icon for legacy macOS versions (Sequia and older) and use a new Icon Composer icon (placed in the project root) for macOS Tahoe 26. Enabling "Include all app icon assets" under target settings ensured that older macOS versions would use the old app icons while Tahoe the new Icon Composer glass one. Since Xcode beta 4 this technique no longer works. Xcode instead insists on populating Assets.car with Icon Composer generated variants, disregarding the App Icon provided in Assets. Although the App Icon in Assets makes its way to a .incs file in the app bundle's Contents/Resources folder, but that is not used by macOS anymore and is there for some compatibility purposes. The Assets.car file (which matters) only contains the variants generated by Icon Composer and does not contain the png icons provided in the Assets.

Archive failing while executing command: xcodebuild -project Unity-VisionOS.xcodeproj -scheme Unity-VisionOS -destination generic/platform=xros archive -archivePath Unity-VisionOS.xcarchive -quiet > logs/visionos_archive.log Next error happens: 2025-11-18 15:33:12.161 ibtoold[56062:4395005] [MT] IBPlatformTool: *** Failed to launch tool with description <IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null): Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'. Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 Device: (null) ** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`.: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Failure reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: ( "IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)", "IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)", "IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)" )): Incompatible device /* com.apple.ibtool.document.warnings */ /Users/xcode_dir_path/xcode/LaunchScreen-iPhone.storyboard:global: warning: Compiling Interface Builder products for visionOS will not be supported in a future version of Xcode. [9] /* com.apple.ibtool.errors */ /Users/xcode_dir_path/LaunchScreen-iPhone.storyboard: error: Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'. Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 Device: (null) ** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`. Underlying Errors: Description: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 Failure Reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: ( "IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)", "IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)", "IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)" ) Underlying Errors: Description: Incompatible device It appears when command was executed from TeamCity. And when it launches manually from console, it works fine. I tried reinstalling SDK, switching different Xcode versions, removing cache, clearing IB folder, nothing helps. xcrun simctl list command prints next: == Device Types == iPhone 17 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro) iPhone 17 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro-Max) iPhone Air (com.apple.CoreSimulator.SimDeviceType.iPhone-Air) iPhone 17 (com.apple.CoreSimulator.SimDeviceType.iPhone-17) iPhone 16 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro) iPhone 16 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro-Max) iPhone 16e (com.apple.CoreSimulator.SimDeviceType.iPhone-16e) iPhone 16 (com.apple.CoreSimulator.SimDeviceType.iPhone-16) iPhone 16 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Plus) iPhone 15 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro) iPhone 15 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro-Max) iPhone 15 (com.apple.CoreSimulator.SimDeviceType.iPhone-15) iPhone 15 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Plus) iPhone 14 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro) ... Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro-4K) Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro) iPod touch (7th generation) (com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-) == Runtimes == iOS 18.1 (18.1 - 22B81) - com.apple.CoreSimulator.SimRuntime.iOS-18-1 iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6 visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 == Devices == -- iOS 18.1 -- iPhone 16 Pro (78683AE0-6238-4EF1-BD47-192FC0DC2559) (Shutdown) iPhone 16 Pro Max (98BFE915-787D-4673-991A-5D3EC448CC51) (Shutdown) iPhone 16 (D3E6FED8-9E65-4141-A31C-FC7EA3492111) (Shutdown) ... iPad mini (A17 Pro) (10F1862E-E27B-42C5-9B02-1FA71D2F4707) (Shutdown) iPad (10th generation) (E6E0D31F-91E4-4D3E-898D-516D79DDD58E) (Shutdown) -- visionOS 2.1 -- Apple Vision Pro (E4D22A75-A38E-4135-9152-EF4D64BEC3F2) (Shutdown)

Subject: Xcode Cloud not detecting ci_scripts/ci_post_clone.sh for Flutter iOS build Description: I'm attempting to build a Flutter iOS app using Xcode Cloud, but the build is failing because Xcode Cloud cannot detect my custom build script located at ci_scripts/ci_post_clone.sh in the repository root. Setup: Repository: https://github.com/GlamTam2000/King-chi-app Branch: ios-build-legacy Xcode Project: flutter_application_1/ios/Runner.xcworkspace Xcode Version specified: 15.4 Issue: The Xcode Cloud build logs consistently show: Post-Clone script not found at ci_scripts/ci_post_clone.sh However, the script file is confirmed to exist in the repository: The file is committed and pushed to GitHub (commit 9bd3aa1) Local git verification: git ls-tree HEAD ci_scripts/ shows the file exists File permissions: 100755 (executable) File location: Repository root /ci_scripts/ci_post_clone.sh What I've tried: Created ci_scripts/ci_post_clone.sh at repository root with executable permissions Ensured Unix line endings (LF, not CRLF) Removed macOS extended attributes Tried both ci_post_clone.sh and ci_pre_xcodebuild.sh scripts Created empty commits to force Xcode Cloud to fetch latest changes Verified the file exists locally and in git history Why I need this script: Flutter requires running flutter build ios --release --no-codesign before Xcode can build, which generates the FlutterGeneratedPluginSwiftPackage that Xcode depends on. Without this script running, the build fails with: Could not resolve package dependencies: the package at '.../FlutterGeneratedPluginSwiftPackage' cannot be accessed Question: Why is Xcode Cloud not detecting the ci_scripts/ci_post_clone.sh file even though it exists in the repository root? Is there a specific configuration in App Store Connect or a Xcode Cloud workflow setting that needs to be enabled for custom scripts to run? Additional files in repository (also not working): .xcode-version at repository root (specifying 15.4) .xcodecloud.yml at repository root (with workflow configuration) Any guidance on how to make Xcode Cloud properly detect and execute custom build scripts would be greatly appreciated. This gives Apple Support all the key information they need to help diagnose why the scripts aren't being detected.